Please address the comments from this code review:

## Overall Comments
- There are several spelling inconsistencies for the new status (e.g., `markRedeemSinging`, `sinnings`) that should be corrected to `Signing` to keep method/variable names consistent and avoid confusion.
- The log context in `makeSigning` (formerly `solveRequest`) still references the old naming pattern; double-check log `msg` and `method` fields throughout to keep terminology aligned with the new `Signing` status.

## Individual Comments

### Comment 1
<location> `packages/sui-indexer/src/storage.ts:333-337` </location>
<code_context>
 	}

-	async markRedeemSolved(redeemId: number): Promise<void> {
+	async markRedeemSinging(redeemId: number): Promise<void> {
 		try {
 			await this.db
 				.prepare("UPDATE nbtc_redeem_requests SET status = ? WHERE redeem_id = ?")
-				.bind(RedeemRequestStatus.Solved, redeemId)
+				.bind(RedeemRequestStatus.Signing, redeemId)
 				.run();
 		} catch (error) {
</code_context>

<issue_to_address>
**issue (typo):** The method name `markRedeemSinging` appears to be a typo and should probably be `markRedeemSigning`.

This looks like an accidental misspelling given that the status and related code use `Signing`. Please rename the method to `markRedeemSigning` and update all its call sites for consistency and clarity.

Suggested implementation:

```typescript
	async markRedeemSigning(redeemId: number): Promise<void> {

```

1. Search the entire codebase for `markRedeemSinging` and rename all call sites to `markRedeemSigning`.
2. If this method is part of a public interface (e.g., exported class), ensure any tests, mocks, or type declarations referencing `markRedeemSinging` are also updated accordingly.
</issue_to_address>

Please address the comments from this code review:

## Overall Comments
- In `RedeemService.processSigningRedeems`, the local variable is named `sinnings` instead of `signings`, which makes the code harder to read; consider renaming it to `signings` (or similar) for clarity.
- Now that the status is `Signing`, consider renaming `processSolvedRedeem` and the related log messages that still say "solved" to use "signing" terminology so the method names and logs consistently reflect the new lifecycle state.

## Individual Comments

### Comment 1
<location> `packages/sui-indexer/src/redeem-service.ts:55-56` </location>
<code_context>
-	async processSolvedRedeems() {
+	async processSigningRedeems() {
 		// NOTE: here we are processing only 50 redeems every minute (every cron), we are not
 		// looping thought all the solved redeems to avoid cloudflare timeout, since we are
 		// already waiting for ika to sign, when calling ikaSdk.getPresignInParicularState
-		const solved = await this.storage.getSolvedRedeems();
</code_context>

<issue_to_address>
**nitpick (typo):** Update the comment to reflect the new `signing` status and fix the minor typo.

This still mentions "solved redeems" even though the function now handles `signing` redeems. Please update the phrase to "signing redeems" and correct the typo "thought" → "through" to match the new flow and fix the wording.

```suggestion
		// NOTE: here we are processing only 50 redeems every minute (every cron), we are not
		// looping through all the signing redeems to avoid cloudflare timeout, since we are
```
</issue_to_address>

### Comment 2
<location> `packages/sui-indexer/src/handler.ts:93-94` </location>
<code_context>
-		await this.storage.markRedeemSolved(Number(e.redeem_id));
+		await this.storage.markRedeemSigning(Number(e.redeem_id));

 		logger.info({
 			msg: "Marked redeem as solved and added inputs",
</code_context>

<issue_to_address>
**suggestion:** Log message still says "solved" although the status is now set to `Signing`.

Since this handler now calls `markRedeemSigning`, please update the log text to say `signing` instead of `solved` to keep status transitions clear in the logs.
</issue_to_address>